Step 4 Verify Deployment
Perform the following verifications:
|
■
|
The Application Gateway displays the backend as healthy. |
|
■
|
http://ump.example.com/tenantui redirects to https://ump.example.com/tenantui. |
|
■
|
Sign-in with Entra ID completes, and you stay signed in when you open other pages. |
|
■
|
The browser address bar shows ump.example.com throughout sign-in, never the VM name or localhost. |
|
■
|
Live updates work in the browser developer tools |
|
■
|
https://ump.example.com/authenticate opens without a redirect loop. |
|
■
|
Single sign-on from UMP-365, and verify that the user stays signed in when they open other pages. |
|
■
|
A bulk upload and a CSV export complete without a 502 or 504 from the gateway. |
|
■
|
From a machine outside the virtual network, ports 443, 1433, 5672 and 15672 on the VM's IP address do not answer. |
|
■
|
From the internet, https://ump.example.com/authenticate/swagger is blocked. |
|
■
|
To view the packets UMP-365 receives from the WAF, set the system environment variable ASPNETCORE_FORWARDEDHEADERS_LOG to true on the VM and recycle TenantUIAppPool. The UMP-365 web application then logs, for every request, the scheme, all request headers and the client IP address it views, at Debug level. You want to see the scheme https and the user's real IP address. Remove the variable when you have completed your review, as it results in the creation of many logs, including cookies. |